Method for communicating with other devices, and communication device

ABSTRACT

One embodiment relates to a method performed by a converged personal network service (CPNS) enabled entity. The communication method comprises a step in which the CPNS enabled entity transmits a request message for instructing performance of a discovery procedure to a first PNE which belongs to a first network if a second PNE which belongs to a second network is not found in the coverage of the first network at the state where the CPNS enabled entity is established as a gateway for managing the first network; a step in which the CPNS enabled entity receives, from the first PNE, a response message; and a step of transmitting, based on the response message, a bridge request message for requesting that the second PNE operates as a bridge for interconnecting the first network and the second network, to a second gateway which manages the second network.

This application is a continuation of U.S. patent application Ser. No.13/702,528, filed on Dec. 6, 2012, now U.S. Pat. No. 8,958,343, which isthe National Stage filing under 35 U.S.C. 371 of InternationalApplication No. PCT/KR2011/004176, filed on Jun. 8, 2011, which claimsthe benefit of U.S. Provisional Application No. 61/352,800, filed onJun. 8, 2010, 61/353,182, filed on Jun. 9, 2010, 61/356,644, filed onJun. 20, 2010, 61/386,954, filed on Sep. 27, 2010, and 61/419,877, filedon Dec. 6, 2010, the contents of which are all hereby incorporated byreference herein in their entirety.

TECHNICAL FIELD

The present invention relates to Converged Personal Network Service(CPNS).

BACKGROUND ART

From among a variety of developed technologies, the existing technology,such as DLNA or ZigBee, has placed emphasis on the search and use of theservices of devices within a specific PAN. Tethering technology hasplaced emphasis on a connection between heterogeneous networks.

In contrast, unlike this simple PAN, a CPNS concept has been proposed.

In CPNS, devices belonging to a Personal Network (PN) (or also called aPersonal Area Network (PAN)) receive several services.

This CPNS is implemented by way of a CPNS server, a CPNS gateway, anddevices which support CPNS. In addition, there may be a common serverand common devices.

In the CPNS, a bundle of devices is called a PN based on a personalnetwork. The CPNS gateway is placed within the PN, the services ofdevices belonging to the PN are registered with the CPNS server throughthe CPNS gateway, a device that provides a specific service can besearched for by the CPNS server, and an external entity can share theservice provided by the device based on the search.

The CPNS gateway functions to connect a PN (also called a gateway ‘GW’)to another network. The CPNS device is also called a Personal NetworkEntity (PNE). The CPNS device is a member of a PN, and several devicesmay be grouped into one PNE or a single device may become a PNE.

FIG. 1 is an exemplary diagram showing a concept of CPNS.

As shown in FIG. 1, common servers, CPNS servers, CPNS gateways, CPNSdevices, and common devices are shown.

The CPNS server can communicate with one or more CPNS gateways (i.e., PNgateway) and transmit and receive data. Each CPNS server can exchangedata by communicating with one or more CPNS devices within a PN (orcalled a Personal Area Network (PAN)) through the CPNS gateway.

Each of the CPNS devices can transmit and receive data to and from oneor more other CPNS devices or common devices through the CPNS gateway.

The CPNS gateway can transmit and receive data by communicating with aCPNS server, a CPNS gateway belonging to another PN, or a CPNS device.

Each CPNS server can transmit and receive data by communicating with acommon server and a CPNS gateway.

For example, the CPNS server and the CPNS gateway can communicate witheach other over a cellular network, and the CPNS gateway and the CPNSdevice can communicate with each other using near-field communication,for example, Bluetooth, NFC, ZigBee, or Wi-Fi.

Meanwhile, the CPNS server manages and controls communication betweenthe CPNS gateway and the CPNS device, and so applications and pieces ofinformation are exchanged, thereby being capable of increasing userexperience. For example, in FIG. 1, a user can obtain positioninformation from another CPNS device (e.g., a GPS) using a specific CPNSdevice, transmit the position information to a CPNS server through theCPNS gateway, and receive position-based service from the CPNS server.

As a result, the user can be provided with various services throughseveral CPNS devices that belong to the PN.

DISCLOSURE Technical Problem

The aforementioned conventional technology has proposed only the conceptof CPNS, but has not proposed a necessary technical specification inorder to implement this CPNS service.

Accordingly, an object of this specification is to provide detailedtechnology for implementing CPNS service.

Technical Solution

In order to achieve the above object, an embodiment of the presentinvention provides a method of communicating with other devices, whichis performed by a communication device including a Converged PersonalNetwork Service (CPNS)-enabled entity. The communication method caninclude the steps of sending a request message for indicating theexecution of a discovery procedure to a first Personal Network Entity(PNE) belonging to a first network if a second PNE belonging to a secondnetwork fails in discovering the coverage of the first network in thestate in which the CPNS-enabled entity is set as a gateway so that theCPNS-enabled entity manages the first network; the CPNS-enabled entityreceiving a response message, including a result of the execution of thediscovery procedure, from the first PNE; and determining whether or notto transmit a bridge request message based on the response message.Here, the bridge request message may be determined to be transmitted ifthe response message includes information on the second PNE belonging tothe second network as the result of the execution of the discoveryprocedure. The communication method can further include the steps ofsending a bridge request message for requesting, from a second gatewaymanaging the second network, that the second PNE operates as a bridgefor coupling the first network and the second network to the secondgateway via the first PNE and the second PNE and sending a bridgerequest message for requesting that the first PNE operates as a bridgefor coupling the first network and the second network to the first PNEwhen a bridge response message is received from the second gateway.

If the bridge response message may include a value indicative ofallowance, the bridge request message is transmitted to the first PNE.If the second gateway receives a positive response from a user, thebridge response message may include the value indicative of theallowance.

The request message for indicating the execution of the discoveryprocedure may be transmitted to several devices within the firstnetwork. The response message may be received from one or more of theseveral devices. The determining step may further include the step ofdetermining whether or not to send the bridge request message via thefirst PNE based on the response message from one or more of the severaldevices. The determining step may further include the step ofdetermining whether or not to operate the second PNE as the bridge basedon the response message from one or more of the several devices.

The CPNS-enabled entity may be a status in which the CPNS-enabled entityis unable to be directly connected with the second PNE, and the secondgateway may be a status in which the second gateway is unable to bedirectly connected with the first PNE.

Meanwhile, in order to achieve the above object, an embodiment of thepresent invention provides a method of communicating with other devices,which is performed by a communication device including a ConvergedPersonal Network Service (CPNS)-enabled entity. The communication methodmay include the steps of receiving a discovery request message,including information on a second gateway managing a second network andinformation on the second network, from a second Personal Network Entity(PNE) belonging to the second network in the state in which theCPNS-enabled entity is set as a first PNE and belongs to a first networkmanaged by a first gateway and comparing the received information on thesecond network with information on the first network. Here, theinformation on the first network might have been obtained in a procedureof setting up a connection with the first gateway. The communicationmethod may further includes the steps of sending an information updaterequest message, including the information on the second network, to thefirst gateway if one or more of the pieces of information are differentand receiving a bridge request message from the first gateway. Here, thebridge request message may be received from the first gateway if a PNEbelonging to the coverage of the first network and the coverage of thesecond network is not present and the first network and the secondnetwork are able to be coupled through the first PNE and the second PNE.The communication method may further include the steps of sending abridge request message for requesting that the second PNE operates as abridge to the second PNE in response to the reception of the bridgerequest message and activating a bridge for coupling the first networkand the second network when a bridge response message is received fromthe second PNE.

The first gateway may be a status in which the first gateway is unableto be directly connected with the second PNE, and the second gateway maybe a status in which the second gateway is unable to be directlyconnected with the first PNE.

When the bridge is activated, a communication link may be set up betweenthe first gateway and the second gateway via the first PNE and thesecond PNE.

Meanwhile, in order to achieve the above object, an embodiment of thepresent invention provides a communication device. The communicationdevice may include a storage unit for storing a Converged PersonalNetwork Service (CPNS)-enabled entity set as a gateway so that theCPNS-enabled entity manages a first network; a transceiver unit forsending a request message for requesting the execution of a discoveryprocedure to a first Personal Network Entity (PNE), belonging to thefirst network, if the CPNS-enabled entity fails in discovering a secondPNE belonging to a second network within the coverage of the firstnetwork and enabling the CPNS-enabled entity to receive a responsemessage, include a result of the execution of the discovery procedure,from the first PNE; and a control unit for determining whether or not tosend a bridge request message based on the response message.

Here, the bridge request message may be determined to be transmitted ifthe response message includes information on the second PNE belonging tothe second network as the result of the execution of the discoveryprocedure.

The transceiver unit may send a bridge request message for requesting,from a second gateway managing the second network, that the second PNEoperates as a bridge for coupling the first network and the secondnetwork to the second gateway via the first PNE and the second PNE ifthe bridge request message is determined to be transmitted and send abridge request message for requesting that the first PNE operates as abridge for coupling the first network and the second network to thefirst PNE when a bridge response message is received from the secondgateway.

Advantageous Effects

An embodiment of the present invention has solved the aforementionedconventional problem. That is, an embodiment of the present inventionproposes detailed technology for implementing CPNS service.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary diagram showing a concept of CPNS.

FIG. 2 is an exemplary diagram showing the entire CPNS procedure.

FIG. 3 shows the architecture of first and second devices shown in FIG.2.

FIG. 4 is an exemplary diagram showing a CPNS-initial procedure.

FIG. 5 shows an example in which the PN of a user A overlaps withanother PN as the user A geographically moves.

FIG. 6 shows a signal flow for operating a specific device as a bridgein accordance with a first embodiment.

FIG. 7 shows a signal flow for operating a specific device as a bridgein accordance with a second embodiment.

FIG. 8 shows a procedure for changing a bridge into another devicedepending on the status of a device in accordance with a thirdembodiment.

FIG. 9 shows a procedure using content or service after operating as abridge in accordance with the first to third embodiments.

FIG. 10 shows an architecture after mode is changed.

FIG. 11 shows an example in which two devices operate as bridges.

FIG. 12 shows a procedure for operating two devices as bridges inaccordance with a fourth embodiment.

FIG. 13 shows a procedure for operating two devices as bridges inaccordance with a fifth embodiment.

FIG. 14 is a block diagram of a device in accordance with theembodiments of the present invention.

MODE FOR INVENTION

The present invention relates to Converged Personal Network Service(CPNS). However, the present invention is not limited to the CPNS andcan be applied to all communication systems and methods and othersystems to which the technical spirit of the present invention can beapplied.

Technical terms used in this specification are used to describe onlyspecific embodiments, and it is to be noted that the terms are notintended to limit the present invention. Furthermore, the technicalterms used in this specification should be interpreted as havingmeanings that are commonly understood by a person having ordinary skillin the art to which the present invention belongs, unless specificallydefined in this specification, and should not be interpreted as havingexcessively comprehensive meanings or excessively reduced meanings.Furthermore, if the technical terms used in this specification areerroneous technical terms that do not precisely represent the spirit ofthe present invention, they should be replaced with technical terms thatmay be correctly understood by a person having ordinary skill in the artand understood. Furthermore, common terms used in the present inventionshould be interpreted according to the definitions of dictionaries oraccording to the context and should not be interpreted as havingexcessively reduced meanings.

Furthermore, an expression of the singular number used in thisspecification includes an expression of the plural number unless clearlydefined otherwise in the context. In this application, terms, such as“comprise” and “include”, should not be interpreted as essentiallyincluding all several elements or several steps described in thespecification and should be interpreted as not including some of theelements or steps or as including additional element or steps.

Furthermore, terms including ordinal numbers, such as the first and thesecond used in this specification, may be used to describe a variety ofelements, but the elements should not be limited to the terms. The termsare used to only distinguish one element from the other element. Forexample, a first element may be named a second element and likewise asecond element may be named a first element without departing from thescope of the present invention.

When it is said that one element is described as being “connected” or“coupled” to the other element, it should be understood that one elementmay be directly connected or coupled to the other element, but a thirdelement may be interposed between the two elements. In contrast, when itis said that one element is described as being “directly connected” or“directly coupled” to the other element, it should be understood that athird element is not interposed between the two elements.

Hereinafter, preferred embodiments according to the present inventionare described in detail with reference to the accompanying drawings. Thesame or similar elements are assigned the same reference numeralsirrespective of reference numerals, and a redundant description thereofis omitted. Furthermore, in describing the present invention, a detaileddescription of the known functions and constructions will be omitted ifit is deemed to make the gist of the present invention unnecessarilyvague. Furthermore, the accompanying drawings are provided to helpeasily understand the spirit of the present invention, and it is to benoted that the spirit of the present invention should not be limited bythe spirit of the present invention. The spirit of the present inventionshould be interpreted as being extended up to all changes, equivalentsto substitutes other than the accompanying drawings.

Although a terminal is illustrated hereafter, the terminal can be calledUser Equipment (UE), Mobile Equipment (ME), a Mobile Station (MS), aUser Terminal (UT), a Subscriber Station (SS), a wireless device, ahandheld device, or an Access Terminal (AT). Furthermore, the terminalcan be a portable device equipped with a communication function, such asa mobile phone, a PDA, a smart phone, a wireless modem, or a notebook,or can be a not-portable device, such as a PC or a device mounted on avehicle.

Definition of Terms

Prior to a description with reference to the drawings, terms used inthis specification are defined in brief in order to help understandingof the present invention.

1) Converged Personal Network Service (CPNS): CPNS enables devices tobelong to a Personal Network (PN) (or also called a Personal AreaNetwork (PAN)) and to receive several services. When comparing this CPNSwith common tethering service, tethering service is technology forallowing a device that has simply accessed the Internet to allocate aprivate IP address to a different device using NAT technology so thatthe different device can access the Internet using the private IPaddress. In contrast, in CPNS, a first device of a user allocates aprivate IP address to other devices and also integrates and managesseveral services that can be provided over a mobile communicationnetwork. When several services are integrated and managed by the firstdevice of the user as described above, the services can be sharedbetween several devices of users seamlessly. For example, a first deviceof a user uses video on demand (VoD) and can transfer the VoD to asecond device seamlessly. Accordingly, user convenience can beincreased. Furthermore, in CPNS, when the user owns several devices, anexternal server can determine that service data must be transmitted towhich one of the several devices when the external server tries totransfer the service data to the user even when there is no request fromthe user. For example, in the case where a user owns several devicescapable of video telephony, when the user receives a video call request,an external server can determine that the video telephony call must betransferred to which one of the several devices. Furthermore, in CPNS,the video call that is in progress can be transferred to another deviceof the user seamlessly. This CPNS is achieved by a CPNS-enabled entitythat is included in a device of a user.

2) a CPNS-enabled entity: the CPNS-enabled entity is a logical entity,and the CPNS-enabled entity can include three types. That is, a PNE, aPN GW, and a CPNS server can be present. A CPNS server entity is placedwithin a core network, and a PNE and a PN GW are placed within CPNSdevice.

3) a CPNS device: the CPNS device can operate in several modes at thesame time within a personal network. The CPNS device has a function ofprocessing, storing, and playing content. Furthermore, the CPNS devicecan have a communication interface that enables other CPNS device tooperate in different modes within a personal network.

4) a CPNS server: The CPNS server is a function entity capable ofproviding resources to CPNS entities in response to a request or in apush manner. The CPNS server registers devices and user-relatedservices, stores corresponding information, and provides theregistration of a PN, that is, a bundle of devices, and the registrationof a service group including a PN and a WAN. Furthermore, the CPNSserver can communicate with external entities, such as a contentproviding server. The CPNS server is the subject that sets a key forauthenticating a device owned by a user in order to perform service overa CPNS framework. Furthermore, the CPNS server registers externallyprovided services and supports searches and/or consumption/providingrequests so that device can consume the services.

5) a Personal Network (PN): the PN is a set of devices that enable usersto consume or generate services. All devices within the PN can beconnected to a PN GW. The PN can be changed over time. The PN caninclude a device at least operating in GW mode and a different deviceoperating as a PNE.

6) a PNE: the PNE is an abbreviation of a Personal Network Element andis a member that forms a PN. The PNE can consume or provide service orcontent. The PNE is the subject that consumes actual content,applications, and service. The PNE is the subject that is a member whenproducing a PN within a CPNS framework and forming a service group.

7) a PN GW: the PN GW is an abbreviation of a Personal Network Gatewayand is an entity that is present within a PN and a wide area network.The PN GW can generate a PN that provides CPNS service. Furthermore, thePN GW is responsible for a connection with a heterogeneous network for adevice that is present within a PN, but is unable to perform an externalconnection. The PN GW registers a CPNS server for connected devices andmanages inventories.

A PN GW within a device allows not only a PNE present within a PN, butalso another device to be connected to a CPNS server. A PN GW presentwithin a device uses a global network, such as a mobile network.Furthermore, a PN GW manages service with PNEs and manages communicationand pieces of other function information.

8) a PN inventory: the PN inventory is a list of PNs, PNs belonging toseveral PNs, and devices.

9) a service group: The service group is a set of PNEs and a PN GW thatshare services, data, and applications. The service group refers to abundle of devices that are registered with a server through a generatedPN. Here, all devices, that is, members of a service group, do not needto be dependent on one PN, and the devices include devices which arespaced apart from one another because they belong to several PNs andcannot be connected. Furthermore, the devices do not need to be devicesowned by the same user.

10) a zone: the zone refers to a specific area zone.

11) zone-based service: the zone-based service refers to a CPNS servicethat is provided within the coverage of a zone-based PN GW.

12) a zone PN GW: the zone PN GW is a PN GW that provides unique serviceor content within a zone.

13) Mode of a CPNS-enabled entity: CPNS device can operate as a PN GW inPNE mode. The mode can be checked between devices through a CPNS entitydiscovery function. A PN has to include at least a device operating as aPN GW and a PNE operating as a PNE. A PNE and a PN GW have to knowmutual modes in order to generate or participate in a PN. A PN GW has tobe able to identify a PNE in order to produce a member of a PN.Furthermore, a PNE has to know a PN GW in order to generate a PN newlyor participate in the existing PN.

If there are devices (e.g., an MP3 player and a smart meter) thatsupport only PNE mode, the devices operate only in PNE mode. If a devicecan operate as only a PN GW, the device operates as a PN GW. If a devicecan operate as any one of a PN GW and a PNE, the mode of the device canoperate as one of the PN GW and the PNE according to a previously storedconfiguration value and can be changed depending on user setting orservice provider setting.

FIG. 2 is an exemplary diagram showing the entire CPNS procedure.

As can be seen with reference to FIG. 2, a first device 110, a seconddevice 120, a CPNS server 300, and an application server 400 are shown.

The first and the second devices 110 and 120 are devices owned by a userA. The first device 110 is a cellular phone of the user A and can beequipped with a first transceiver for connecting to the CPNS server 300over a mobile communication network. Furthermore, the first device 110can include a second transceiver, such as Bluetooth, Wi-Fi, or ZigBee,so that it can form a personal network. The second device 120 is aportable multimedia device of the user A. The second device 120 does notinclude a first transceiver capable of communication with a mobilecommunication network and can include only a second transceiver, such asBluetooth, Wi-Fi, or ZigBee capable of forming a personal network.

The first and the second devices 110 and 120 can include CPNS-enabledentities. Each of the CPNS-enabled entities can operate in gateway modeor Personal Network Entity (PNE) mode. FIG. 2 illustrates that thesecond device 120 operates as a gateway because it includes a firsttransceiver capable of a connection over a mobile communication network.

The first device 110 and the second device 120 first perform a physicalconnection procedure through the second transceivers when they arelocated at a long distance. Meanwhile, the application server 400registers service and content with the CPNS server 300 or advertises theservice and content. Furthermore, the CPNS server 300 performs aprocedure of authenticating the second device 120 that operates as thegateway.

Meanwhile, when the first device 110 and the second device 120 completethe physical connection procedure, the CPNS-enabled entities of thefirst device 110 and the second device 120 perform procedures ofsearching for them.

When the searches are completed, the devices configure PN#1. Here,information on the PN#1 is registered with the CPNS server 300.

When the configuration of the PN#1 is completed, the CPNS server 300advertises its own services to the devices within the PN#1 or performs aprocedure of searching for services that can be provided by the deviceswithin the PN#1.

When a specific device within the PN#1 invokes specific service orcontent among the advertised services, a procedure of checking thefunction of the specific device is performed and the specific service orcontent is transferred to the specific device according to the checkedfunction.

When the specific device uses the specific service or content, usestatistics are gathered and reported to the CPNS server 300 or theapplication server 400.

Meanwhile, if the PN#1 is no longer necessary, the PN#1 is released andinformation on the PN#1 can be deregistered from the CPNS server 300.

FIG. 3 shows the architecture of the first and second devices shown inFIG. 2.

As can be seen with reference to FIG. 3, a physical layer, an MAC layer,a 3^(rd) layer, a CPNS-enabled entity, and an application layer arepresent in each of the first and the second devices 110 and 120. Here,the CPNS-enabled entity of the second device 120 operates in PNE mode,and the CPNS-enabled entity of the first device 110 drives only agateway entity. In contrast, the CPNS-enabled entity of the first device110 drives a gateway entity.

Accordingly, as indicated by a thick solid line in FIG. 3, service datais transferred to the gateway entity within the CPNS-enabled entity ofthe first device 110 via the physical layer, the MAC layer, and the3^(rd) layer of the first device 110. When the gateway entity of thefirst device 110 receives the service data, the service data istransferred to the second device 120 via the CPNS-enabled entity, the3^(rd) layer, the MAC layer, and the physical layer of the first device110.

In the second device 120, the PNE of the CPNS-enabled entity receivesthe service data via the physical layer, the MAC layer, and the 3^(rd)layer.

Meanwhile, the PNE within the CPNS-enabled entity of the second device120 transmits a control message, such as a request message or a responsemessage, to the first device 110 via the 3^(rd) layer, the MAC layer,and the physical layer.

FIG. 4 is an exemplary diagram showing a CPNS-initial procedure.

As can be seen with reference to FIG. 4, a paring procedure S11corresponding to a physical connection procedure, an entity discoveryprocedure S12, and a PN establishment procedure S13 are performed.

First, the paring procedure S11 is described. In the state in whichthere is no connection between the devices of a user A, a physicalconnection is initiated between the shown devices.

To this end, a second device 120 starts scan. To this end, the seconddevice can transmit a scan message to the first device 110. The firstdevice 110 transmits a scan response message to the second device 120 inorder to respond to the scan. In response thereto, a procedure for aphysical connection is initiated and pieces of information for thephysical connection, for example, an address and an IP address areexchanged between the first device and the second device. After thepieces of information are exchanged, the second device transmits aphysical connection request message, for example, a paring requestmessage to the first device. The first device receives a pin code fromthe user and transmits a connection request response message includingthe pin code, for example, a paring response message to the seconddevice. If the pin code is correct, the physical connection procedure iscompleted.

Meanwhile, when the physical connection is completed, each of theCPNS-enabled entities within the devices performs a procedure fordiscovering them, that is, the entity discovery procedure S12.

Concretely, first, the CPNS-enabled entity of the second device 120transmits a discovery request message, for example, an entity discoveryrequest message to the first device 110. The discovery request message,for example, the entity discovery request message includes informationon mode of the CPNS-enabled entity within the second device andinformation on the CPNS-enabled entity and other devices previouslyretrieved. Here, if the CPNS-enabled entity within the second device isset as a gateway, the mode information can include informationindicative of the gateway.

Meanwhile, the CPNS-enabled entity of the first device 110 alsotransmits a discovery request message, for example, an entity discoveryrequest message to the second device 120. Likewise, the discoveryrequest message, for example, the entity discovery request messageincludes information on mode of the CPNS-enabled entity within the firstdevice 110 and information on the CPNS-enabled entity and other devicespreviously retrieved. Here, if the CPNS-enabled entity within the firstdevice is set as a Personal Network Entity (PNE), the mode informationcan include information indicting the PNE.

In response to the discovery request message received from the seconddevice, the CPNS-enabled entity of the first device 110 transmits adiscovery response message, for example, an entity discovery responsemessage to the second device 120. The discovery response message, forexample, the entity discovery response message includes the modeinformation, the information on the CPNS-enabled entity and otherdevices previously retrieved, and information on a UI function.

Likewise, in response to the discovery request message received from thefirst device, the CPNS-enabled entity of the second device 120 transmitsa discovery response message, for example, an entity discovery responsemessage to the first device 110.

When the discovery procedure is completed by the above signals, the PNestablishment procedure S13 is performed.

Concretely, if the CPNS-enabled entity of the second device 120 is setas a gateway, a PN setup request message is transmitted to a device setas a PNE, for example, the first device 110. Here, the PN setup requestmessage can include information on the gateway and information onentities to be included in a PN that will be generated (e.g., aCPNS-enabled entity within the first device).

When the CPNS-enabled entity of the first device transmits a PN setupresponse message to the second device, the CPNS-enabled entity of thesecond device 120 transmits a PN setup request message to the CPNSserver 300.

When the PN setup request message is received, the CPNS server 300transmits an authentication request message to the first device throughthe second device 120 that operates as the gateway. In response to theauthentication request message, the first device transmits anauthentication response message to the CPNS server 300 through thesecond device that operates as the gateway.

When the authentication response message is received, the CPNS server300 transmits the PN setup response message to the second device 120that operates as the gateway.

In response thereto, the CPNS-enabled entity of the second device 120that operates as the gateway transmits a PN establishment-completenotify message to the first device.

When the establishment of the PN is completed by the transmission andreception of the messages, the application server 400, such as a contentserver, can transfer a service description advertisement message,including information on its own service, to the second device 120, thatis, the gateway, through the CPNS server 300. In response thereto, thesecond device 120, that is, the gateway, transfers the servicedescription advertisement message to devices that belong to the PNmanaged by the second device 120.

FIG. 5 shows an example in which the PN of a user A overlaps withanother PN as the user A geographically moves.

First, FIG. 5(a) illustrates two PNs, a CPNS server, and an applicationserver. The PN#1 of the two PNs has been generated by a user A. The PN#1includes the devices of the user A and can include, for example, a GW#1,a PNE#2, and a PNE#3 as shown. It is here assumed that the GW#1 is thecellular phone of the user A and the PNE#2 and the PNE#3 are theportable multimedia devices of the user A. Meanwhile, the PN#2 of thetwo PNs includes a GW#2 and a PNE#4. The application server can provideservice to the PNEs within the PNs through the CPNS server and the GW#1and the GW#2.

Meanwhile, as shown in FIG. 5(b), it is assumed that the user A has gotoff a vehicle with the GW#1 left in the vehicle and has geographicallymoved and moved within the coverage of the PN#2 in the state in whichthe user A carries only the PNE#2 and the PNE#3. In this case, it isassumed that the PNE#3 is unable to communicate with the GW#2 becausethe communication method of the PNE#3 is different from thecommunication method of the GW#2 of the PN#2.

In this situation, there is a problem in that although the user A wantsto receive service provided by the PN#2 through the PNE#3, the user Acannot receive the service because the PNE#3 cannot communicate with theGW#2.

In order to solve this problem, the PNE#2 must perform communicationwith the GW#2, receive the service from the GW#2, and transmit theservice to the PNE#3 as shown. That is, the PNE#2 must operate as abridge.

Meanwhile, as shown in FIG. 5(c), it is assumed that the user A hasgeographically moved and moved within the coverage of the PN#2 in thestate in which the user A carries the GW#1, the PNE#2, and the PNE#3.

In this situation, if the user A wants to receive service provided bythe PN#2 through the PNE#3, the PNE#2 may operate as a bridge, receiveservice from the GW#2, and transmit the service to the PNE#3 or thePNE#3 may operate as a bridge and receive the service from the GW#2.When two or more PNEs operate as bridges as described above, there maybe a problem in that which PNE has to be selected.

Accordingly, a scheme for operating a PNE as a bridge and a scheme forselecting a bridge are hereinafter described.

FIG. 6 shows a signal flow for operating a specific device as a bridgein accordance with a first embodiment.

As can be seen with reference to FIG. 6, the first embodimentillustrates a detailed procedure in which a specific device, forexample, a second device 120 is made to operate as a bridge.

The first embodiment of FIG. 6 illustrates that a determination ofwhether a specific one of the devices of a user A will be operated as abridge or not and if a specific device has to be operated as a bridge,which device will be operated as the bridge is performed by a CPNSserver.

Concretely, as can be seen with reference to FIG. 6, the user A owns afirst device 110 operating as a gateway (e.g., a GW#1), the seconddevice 120 operating as a PNE#2, and a third device 130 operating as aPNE#3. It is assumed that the first device 110 is a cellular phone andthe second device 120 and the third device 130 are portable multimediadevices.

1) When the first device 110, the second device 120, and the thirddevice 130 are located a short way off, a physical connection procedureis performed. Here, a CPNS-enabled entity within the first device 110reads in its own mode setting value, activates a gateway entity based onthe mode setting value, and deactivates a PNE. Likewise, CPNS-enabledentities within the second device 120 and the third device 130 read intheir own mode setting values, activate their PNEs based on the modesetting values, and deactivate their gateway entities.

2) Next, a mutual discovery procedure is performed between the firstdevice 110, the second device 120, and the third device 130.

3) Furthermore, the first device 110, the second device 120, and thethird device 130 generate a PN#1 by performing a PN establishmentprocedure therebetween.

4) Meanwhile, it is assumed that the user A has geographically moved andmoved within the coverage of a PN#2 in the state in which the user Acarries the second device 120. It is here assumed that the PN#2 ismanaged by a fourth device 210 operating as a gateway (e.g., a GW#2).

It is here assumed that the user A wants to receive service, provided bythe PN#2, using the third device 130 that is not located within thecoverage of the PN#2.

When the user A has geographically moved and moved within the coverageof the PN#2 in the state in which the user A carries the second device120, the fourth device 210 within the PN#2 performs a physicalconnection procedure.

Concretely, the fourth device 210 can transmit a scan message to thesecond device 120. The second device 120 transmits a scan responsemessage to the fourth device 210 in response to the scan. In responsethereto, the second device 120 initiates a procedure for a physicalconnection with the fourth device 210, and pieces of information for thephysical connection, for example, an address and an IP address areexchanged between the second device 120 and the fourth device 210. Afterthe pieces of information are exchanged, the fourth device 210 transmitsa physical connection request message, for example, a paring requestmessage to the second device 120. The second device 120 transmits aconnection request response message, for example, a paring answermessage to the fourth device 210.

5) When the physical connection is completed, the CPNS-enabled entitywithin the fourth device 210 transmits a discovery request message tothe second device 120 right after the physical connection is completedif its own mode is set as a gateway. Here, if the CPNS-enabled entitywithin the fourth device 210 does not transmit the discovery requestmessage first, but the second device 120 transmits the discovery requestmessage at the same time, pieces of information can overlap with eachother. In order to prevent this problem, the fourth device 210 operatingas a gateway first transmits the discovery request message right afterthe physical connection is completed.

Meanwhile, the discovery request message can include the followingelements.

-   -   EntityInfo element: It includes information on a CPNS-enabled        entity that transmits a discovery request message.    -   UserInfo element: It includes information on the user of a        CPNS-enabled entity that transmits a discovery request message.        The information on the user can include a user ID lower element        and a user name lower element.    -   PNEID element (or attribute): It is the ID of a PNE when a        CPNS-enabled entity that transmits a discovery request message        is the PNE.    -   PN GW ID element (or attribute): It is the ID of a GW when a        CPNS-enabled entity that transmits a discovery request message        is a PN GW.    -   PNE Name or PN GW Name element: It is the name of a PNE when a        CPNS-enabled entity that transmits a discovery request message        is the PNE or it is the name of a GW when a CPNS-enabled entity        that transmits a discovery request message is a PN GW.    -   Mode element (or attribute): It is information on activated mode        of a CPNS-enabled entity that transmits a discovery request        message, and the information has a value indicative of a PNE or        a PN GW. If activated mode of the CPNS-enabled entity is a PNE,        it has a value of 1. If activated mode is a PN GW, it has a        value of 2. In FIG. 10, a value of 2 is included because the        CPNS-enabled entity of a third device has been set as a gateway.    -   PN Info Req element (or attribute): It has a true value or false        value, and a true value is included in the PN Info Req element        (or attribute) when a CPNS-enabled entity that transmits a        discovery request message wants to obtain information on a PN        stored by an entity that will receive the discovery request        message.    -   UI Capabilities element (or attribute): It has a true value when        a PN GW has to perform a user interaction instead of a PNE. The        UI Capabilities element (or attribute) is set by a PNE. For        example, when a PNE does not have a user interface, the UI        Capabilities element (or attribute) can be set as a true value        if a PN GW instead has to perform an interaction with a user.    -   Zone based service support element (or attribute): It is set as        “true” when a PN GW can provide zone-based service.    -   PN Info element: It is an element included when a CPNS-enabled        entity that transmits a discovery request message is a PN GW.        The PN Info element includes a PN ID lower element, a PNE Info        lower element, etc. If a PN is already present, the PN ID lower        element indicates an ID for the PN, and if a PN is already        present, the PNE Info lower element includes information on a        PNE that belongs to the PN. The PNE info lower element includes        a PNE ID element and a PNE Name element.

The above-described discovery request message can be the same as Table 1below.

TABLE 1 ELEMENT DESCRIPTION UserInfo Includes UserID and UserName.UserID ID of a CPNS user UserName Name of a CPNS user EntityInfo It isan abbreviation of entity information and it can include PNEID, PNGWID,Name, Mode, PN Info Req, UI Capa, Zone based service support, andBroadcast group key delivery support element. PNEID ID of a PNE PNGWIDPN ID of a GW Name name of PNE or PN GW Mode Mode of the subject thatperforms transmission. If a PNE performs transmission, mode has a valueof 1. If a PN GW performs transmission, mode has a value of 2. If a PNEand a GW can operate at the same time, mode has a value of 3. PNInfoReqIt is set as tree when PN Info is requested if a PNE sends a message.UICapa It is set as true if a PN GW interacts with a user because adevice operating as a PNE does not have a user interface. Zone based Itis set as true if a PN GW provides zone-based service. service supportPN Info It includes information on a PN so that a PNE can join the PN ifthe subject that transmits a discovery request message is a PN GW andhas the PN. PN Info can include a PN ID, Description, and PNE Info lowerelement. PNID ID of a PN Description Description of PN PNE Info Itincludes information on PNEs, that is, members of a PN. It can include aPNEID and a PNE Name as lower elements. It can also include Device Infoas a lower element. PNEID ID of a PNE PNEName Name of a PNE Device It isinformation on a device. It can include Mode Info element andInactiveMode. Mode It can include information on mode that is nowactivated. Inactive It includes information on Mode deactivated mode.

Thus, the CPNS-enabled entity of the second device 120 checks an elementfor service, for example, Zone based service support within the receiveddiscovery request message.

Furthermore, the CPNS-enabled entity within the second device 120 checksthat a counterpart that has sent the message is in what mode through aMode element based on the received message and checks the ID of thecounterpart through an Entity Info element.

If checked mode of the counterpart is the gateway GW#2, the CPNS-enabledentity within the second device 120 determines not to transmit adiscovery request message additionally and generates a discoveryresponse message. Here, the generated discovery response message caninclude the following elements.

-   -   Entity Info element: It is information on a CPNS-enabled entity        that has received a discovery request, and the Entity Info        element includes a user ID lower element and a user name lower        element.    -   PNE ID element: It includes the ID of a PNE when a CPNS-enabled        entity that has received the discovery request is the PNE.    -   PNE Name element: It includes the name of a PNE when a        CPNS-enabled entity that has received the discovery request is        the PNE.    -   Mode element: It includes a value indicative of PNE mode.    -   UI Capa element: It has a true value when a PN GW performs a        user interaction instead of a PNE. The UI Capa element is set by        a PNE. For example, if a PNE does not have a user interface and        a PN GW instead performs a user interaction with a user, the UI        Capa element can be set to a true value.    -   PN Info element: If the value of a PN Info Req element within        the received discovery request message is set as true, the PN        Info element is included. If the value of the PN Info Req        element within the received discovery request message is set as        True, the second device 120 operating as a PNE includes        information on the PN#1, already configured along with the first        device 110, in the PN Info element. The PN Info element can        include a PN ID element, a Description element, etc in its lower        position.    -   PNE Info element: It includes information on members of a PN.

The above-described discovery response message can be the same as Table2 below.

TABLE 2 ELEMENT DESCRIPTION UserInfo Include UserID and UserName. UserIDID of a user UserName Name of a user EntityInfo It is an abbreviation ofentity information and it can include PNEID, PNGWID, Name, Mode, PN InfoReq, and UI Capa element. PNEID ID of a PNE PNGWID ID of a PN GW NameName of a PNE or PN GW Mode Mode of the subject that transmits adiscovery response message. It has a value of 1 when a PNE transmits thediscovery response message and a value of 2 when a PN GW transmits thediscovery response message. If the subject can operate as a PNE and a GWat the same time, mode has a value of 3. UICapa It is set as true if aPN GW interacts with a user because a device operating as a PNE does nothave a user interface. PN Info PN Info includes information on a PN ifthe subject that transmits a Discovery Response message is a PNE and thePNE already participates in another PN. PN Info can include a PN ID,Description, and PNE Info lower element. PNID ID of a PN DescriptionDescription of a PN PNEInfo It includes information on PNEs, that is,members of a PN. It can include a PNEID and a PNE Name as lowerelements. It can also include Device Info as a lower element. PNEID IDof a PNE PNEName Name of a PNE DeviceInfo It is information on a device.It can include a Mode element and InactiveMode. Mode It can includeinformation on mode that is now activated. InactiveMode It includesinformation on deactivated mode.

When the discovery response message is received from the second device120, the fourth device 210 checks elements within the discovery responsemessage. That is, the fourth device 210 checks that the second deviceoperates in what mode by checking a Mode element based on the receiveddiscovery response message and also checks what devices are included inthe PN#1 and that the devices operate in what mode by checking a PN Infoelement additionally.

6) Meanwhile, when the discovery procedure is completed based on theabove signals, the fourth device 210 performs a PN establishmentprocedure.

Concretely, the fourth device 210 starts a PN#2 establishment procedurein order to enlist the second device 120 in its own PN#2. Concretely,the CPNS-enabled entity of the fourth device 210 transmits a PN setuprequest message to the second device 120. Here, the PN setup requestmessage can include information on the gateway and information onentities (e.g., the CPNS-enabled entity within the first device) thatwill belong to a PN to be generated.

The PN setup request message can be the same as Table 3 below.

TABLE 3 ELEMENT DESCRIPTION Origin ID of a CPNS-enabled entity thattries to set up a PN Entity ID PN Setup It indicates how PN should beset up. 1: a PN GW and a PNE are included in a Type one-to-one manner.2: A PNE sets up a PN with all devices connected to a PN GW. 3: A PN isset up with only specific invited PNEs. Invited It includes the IDs ofPNEs to be invited during a PN setup process. PNE ID PN Info It isinformation on a PN that will be registered and stored in a CPNS serverand can include PNID, Description, Disclosure, Ownership Entity, PN GWInfo, and PNE Info element. PN ID Indicate the ID of a PN. DescriptionDescription (e.g., home, office) of a PN PN GW Info It is information ona PN GW and includes PNGWID and PN GW Name elements. PNGWID ID of a PNGW PN GW Name Name of PN GW PNE Info It is information on a PNE and caninclude PNEID, PNE Name, Mode, Description, Device Capa, and ServiceProfile elements. PNE ID ID of a PNE PNE Name Name of a PNE ModeInformation on mode of a PNE Description Description of a PN Device CapaInformation on the function of a device including a PNE. Service ProfileInformation on a CPNS-enabled application or information on contentsupporting specific service or state Auth It is information used tostart a PNE authentication procedure and can include IniData Auth PNEID,rand_PNE, and LocalEUKeyAssignment. Auth PNEID ID of a target PNE thatshould be authenticated by a CPNS server rand_PNE Random value generatedby a PNE LocalEUKeyAssignment Flag indicating the necessary ofLocalEUKey allocation TRUE: necessary, and FALSE: unnecessary

When a PNE receives the PN setup request message from the CPNS-enabledentity of the second device 120, the PNE checks an Origin Entity IDelement in order to know that who tries to generate a PN. Furthermore,the PNE extracts PN ID and Msg ID elements from the message.

Furthermore, the CPNS-enabled entity operating as a PNE within thesecond device 120 generates a PN setup response message as follows.

First, the CPNS-enabled entity operating as the PNE includes theresponse to the PN setup request message in a Return element within thePN setup response message. The response is 1 in the case of a successand 2 in the case of a failure. Next, the PNE includes a PN Info elementfor information on a PN, owned by the CPNS-enabled entity of the seconddevice 120, in the PN setup response message. Next, the PNE includesinformation on a PNE, belonging to the PN owned by the CPNS-enabledentity of the second device 120, in a PNE Info element within the PNsetup response message. Furthermore, the PNE includes some elements inthe PN setup response message.

The generated message can be the same as Table 4 below.

TABLE 4 ELEMENT DESCRIPTION Return Indicate whether a PN setup requestis successful or not. 1: OK, 2: fail and the request cannot be processedby a CPNS-enabled entity, and 3: not allowed. PN Info It is informationon a PN and can include PNID, Description, PNGWInfo, and PNEInfo. PN IDID of a PN Description Description of a PN PN GW Info It is informationon a PN GW and can include PNGWID and PN GW Name. PNGWID PN ID of a GWPNGW Name Name of a PN GW PNE Info It is information on a PNE and caninclude PNEID, PNEName, Mode, Description, DeviceCapa, andServiceProfile. PNEID ID of PNE PNEName name of PNE Mode Information onmode of a device Description Description of a PN Device Capa Informationon the function of a device including a PNE Service Profile Informationon a CPNS-enabled application or information on content supportingspecific service or state AuthIniData It is information used to start aPNE authentication procedure and can include Auth PNEID, rand_PNE, andLocalEUKeyAssignment. Auth PNEID ID of a target PNE that should beauthenticated by a CPNS server rand_PNE Random value generated by a PNELocalEUKeyAssignment Flag indicating the necessary of LocalEUKeyallocation TRUE: necessary, and FALSE: unnecessary Auth FinData It isinformation used to by a PNE in order to authenticate a CPNS server andincludes HASH. HASH Hash value calculated by a target PNE or PN GW

When the generation of the PN setup response message is completed, theCPNS-enabled entity of the second device 120 transmits the generatedmessage to the fourth device 210.

When the CPNS-enabled entity of the fourth device 210 receives the PNsetup response message, the CPNS-enabled entity of the fourth device 210checks a Return element within the received message in order to knowwhether the second device 120 wants to participate in the PN. If thevalue of the Return element is set to 1, the CPNS-enabled entity of thefourth device 210 generates information on a PN inventory for the PN,generates a routing table based on information from the receivedmessage, and maintains the routing table.

Meanwhile, the CPNS-enabled entity of the fourth device 210 generates aPN setup request message to be transmitted to the CPNS server.

Concretely, the CPNS-enabled entity of the fourth device 210 includesthe ID of a PN GW in an OriginEntityID element. Furthermore, theCPNS-enabled entity of the fourth device 210 includes information on aPN to be generated in the PN Info element of the PN setup requestmessage. Here, the PN Info element includes a PN ID element includingthe ID of the PN generated by the PN GW, a Description element includinga description of the generated PN, etc. Furthermore, the CPNS-enabledentity of the fourth device 210 includes a PN GW Info element in the PNsetup request message. Here, the PN GW Info element includes a PN GW IDelement indicative of the ID of the PN GW and a PN GW Name elementindicative of the name of the PN GW. Furthermore, the CPNS-enabledentity of the fourth device 210 includes a PNE Info element and an AuthIni Data element in the PN setup request message.

When the generation of the PN setup request message is completed asdescribed above, the CPNS-enabled entity of the fourth device 210transmits the generated PN setup request message to the CPNS server 300.

When the CPNS server 300 receives the PN setup request message from thefourth device 210, the CPNS server 300 generates an authenticationrequest message and transmits the authentication request message to thesecond device 110 through the fourth device 210.

The second device 120 transmits an authentication response message tothe CPNS server 300 through the fourth device 210.

If, as a result of the check of the authentication response message, theauthentication is successful, the CPNS server 300 registers the PNinformation included in the PN setup request message and stores the PNinformation in a PN inventory.

The CPNS server 300 sends a PN setup response message and transmits thePN setup response message to the fourth device 210.

When the fourth device 210 receives the PN setup response message fromthe CPNS server, the fourth device 210 stores the PN information in itslocal PN inventory. Furthermore, the third device 210 generates a PNestablishment notification message and transmits the PN establishmentnotification message to the second device 120.

7) Meanwhile, when the PN#2 establishment procedure is completed asdescribed above, a bridge determination procedure is performed.

Concretely, the CPNS server 300 determines whether or not one of deviceswithin the PN#1 of the user A has to be operated as a bridge. If it isdetermined that one of the devices within the PN#1 of the user A has tobe operated as a bridge, the CPNS server 300 determines the subject thatmust be operated as the bridge from among the devices. In FIG. 6, it isassumed that the second device 200 has been determined to operate as thebridge.

When the second device 120 is determined to operate as the bridge, theCPNS server 300 transmits a bridge request message to the second device120 through the fourth device 210. The bridge request message caninclude the ID of the subject that is determined as the bridge.

When the second device 120 receives the bridge request message, thesecond device 120 transmits the bridge request message to the firstdevice 110, that is, the gateway of the PN#1 to which the second device120 belongs.

When the first device 110 receives the bridge request message, the firstdevice 110 determines whether or not to operate the second device 120 asthe bridge based on user setting, etc.

If it is determined that the second device 120 is operated as thebridge, the first device 110 transmits a bridge response message,including an indicator indicative of allowance, to the second device120. The bridge response message can further include information on thePN#1. Furthermore, the bridge response message can include informationon the status of devices that belong to the PN#1.

When the second device 120 receives the bridge response message, thesecond device 120 checks whether or not a bridge operation is allowed bychecking the indicator within the bridge response message.

If it is checked that the bridge operation is allowed based on theindicator, the second device 120 activates the bridge and transmits thebridge response message to the CPNS server 300 through the fourth device210.

Meanwhile, if there is service data to be provided to the user A, theillustrated application server 400 transmits an information requestmessage to the CPNS server 300 because it does not know that the devicesof the user A are located where and that it has to transmit the servicedata to what device. The information request message can include the IDof the user A.

When the CPNS server 300 receives the information request message, theCPNS server 300 checks that the devices of the user A are located wherebased on the ID of the user A. If it is checked that the second device120 of the user A is located within the coverage of the PN#2, the CPNSserver 300 transmits information, indicating that the second device 120operates as the bridge, to the application server 400.

The application server 400 can transmit service data to the seconddevice 120 of the user A based on the information.

As described above, in the first embodiment, the procedure in which aspecific device, for example, the second device 120 is made to operateas the bridge has been described.

FIG. 7 shows a signal flow for operating a specific device as a bridgein accordance with a second embodiment.

As can be seen with reference to FIG. 7, unlike the first embodiment,the second embodiment illustrates that a determination of whether aspecific one of the devices of a user A will be operated as a bridge andif a specific device has to be operated as a bridge, which device willbe operated as the bridge is performed by a fourth device 210 operatingas a gateway.

Concretely, as can be seen with reference to FIG. 7, the user A owns afirst device 110 operating as a gateway (e.g., a GW#1), a second device120 operating as a PNE#2, and a third device 130 operating as a PNE#3.It is assumed that the first device 110 is a cellular phone and thesecond device 120 and the third device 130 are portable multimediadevices.

1) When the first device 110, and the second device 120 and the thirddevice 130 are located a short way off, a physical connection procedureis performed. Here, a CPNS-enabled entity within the first device 110reads in its own mode setting value, activates a gateway entity based onthe mode setting value, and deactivates a PNE. Likewise, a CPNS-enabledentity within each of the second device 120 and the third device 130reads in its own mode setting value, activates a PNE based on the modesetting value, and deactivates a gateway entity.

2) Next, a mutual discovery procedure is performed between the firstdevice 110, the second device 120, and the third device 130.

3) Furthermore, first device 110, the second device 120, and the thirddevice 130 generate a PN#1 by performing a PN establishment proceduretherebetween.

4) Meanwhile, it is assumed that the user A has geographically moved andmoved within the coverage of the PN#2 in the state in which the user Acarries the first device 110, the second device 120, and the thirddevice 130. It is here assumed that a PN#2 is managed by the fourthdevice 210 operating as a gateway (e.g., a GW#2). It is here assumedthat the user A wants to receive service provided by the PN#2.

When the user A geographically moves and moves within the coverage ofthe PN#2 in the state in which the user A carries the devices 110, 120,and 130, the fourth device 210 within the PN#2 performs a physicalconnection procedure with one or more of the devices 110, 120, and 130.

5) When the physical connection is completed, a CPNS-enabled entitywithin the fourth device 210 transmits a discovery request message rightafter the physical connection is completed if its own mode is set as agateway. This is similar to the description of FIG. 6, and thus adetailed description thereof is omitted.

The CPNS-enabled entity within a device that has received the discoveryrequest message checks mode of a counterpart that has transmitted themessage through the Mode element based on the received message andchecks the ID of the counterpart through an Entity Info element.

If it is determined that mode of the checked counterpart is the gatewayGW#2, the CPNS-enabled entity determines not to transmit a discoveryrequest message additionally and generates and transmits a discoveryresponse message. This is similar to the description of FIG. 6, and thusa detailed description thereof is omitted.

When the discovery response message is received, the fourth device 210checks elements within the discovery response message. That is, thefourth device 210 checks that the devices operate in what mode bychecking a Mode element based on the received discovery response messageand further checks that there are what devices within the PN#1 and thedevices operate in what mode by checking a PN info element based on thereceived discovery response message.

6) Meanwhile, when the discovery procedure is completed, a bridgedetermination procedure is performed. Concretely, the fourth device 210determines whether or not to operate one of the checked devices as abridge based on the received discovery response message. If one of thechecked devices is determined to be operated as a bridge, the fourthdevice 210 also determines the subject that must be operated as a bridgefrom among the devices.

In FIG. 7, for example, the fourth device 210 determines to operate thethird device 130, that is, a PNE#3, as a bridge. According to thedetermination, the fourth device 210 transmits a bridge request messageto the third device 130. Here, the bridge request message can includethe ID of the subject (i.e., the ID of the PNE#3) that is determined asa bridge.

When the third device 130 receives the bridge request message, the thirddevice 130 transmits the bridge request message to the first device 110,that is, the gateway of the PN#1 to which the third device 130 belongs.

When the first device 110 receives the bridge request message, the firstdevice 110 determines whether or not to operate the third device 130 asa bridge based on user setting, etc. If the third device 130 isdetermined not to be suitable for being operated as a bridge based onthe user setting, etc., the first device 110 transmits a bridge responsemessage, including an indicator indicative of denial, to the thirddevice 130. Here, the bridge response message can further include one ormore of user configuration information and information on a device thatis suitable for being operated as a bridge.

When the third device 130 receives the bridge response message, thethird device 130 checks whether a bridge operation is allowed or not bychecking the indicator within the bridge response message. If it ischecked that the bridge operation is denied by the indicator, the thirddevice 130 transmits the bridge response message to the fourth device210.

When the bridge response message is received, the fourth device 210checks whether the bridge operation is allowed or not by checking theindicator within the bridge response message. If it is checked that thebridge operation is denied by the indicator, the fourth device 210determines a device suitable for being operated as a bridge based on oneor more of user configuration information and information on apreference device which are included in the bridge response message.

In FIG. 7, for example, the fourth device 210 determines that the seconddevice 120, that is, the PNE#2, operates as a bridge.

The fourth device 210 transmits the bridge request message to the seconddevice 120.

When the second device 120 receives the bridge request message, thesecond device 120 transmits the bridge request message to the firstdevice 110, that is, the gateway of the PN#1, to which the second device120 belongs.

When the first device 110 receives the bridge request message, the firstdevice 110 determines whether or not to operate the second device 120 asa bridge based on user setting, etc.

If the second device 120 is determined to be operated as a bridge, thefirst device 110 transmits a bridge response message, including anindicator indicative of allowance, to the second device 120. The bridgeresponse message can further include information on the PN#1.Furthermore, the bridge response message can further include informationon the status of the devices belonging to the PN#1.

When the second device 120 receives the bridge response message, thesecond device 120 checks whether a bridge operation is allowed or not bychecking the indicator within the bridge response message.

If it is checked that the bridge operation is allowed by the indicator,the second device 120 activates the bridge and transmits a bridgeresponse message to the fourth device 210.

7) Meanwhile, after the second device 120 is determined as the bridge byway of the aforementioned procedures, the second device 120 and thefourth device 140 perform a PN#2 establishment procedure.

Meanwhile, if an illustrated application server 400 has service data tobe transmitted to the user A, the application server 400 transmits aninformation request message to a CPNS server 300 because it does notknow that the devices of the user A are located where and the servicedata has to transmitted to which device. The information request messagecan include the ID of the user A.

When the CPNS server 300 receives the information request message, theCPNS server 300 checks that the devices of the user A are located wherebased on the ID of the user A. If it is checked the second device 120 ofthe user A is located within the coverage of the PN#2, the CPNS server300 transmits information, indicating that the second device 120operates as a bridge, to the application server 400.

The application server 400 can transmit the service data to the seconddevice 120 of the user A based on the information.

In the second embodiment, an example in which a determination of whethera specific one of the devices of a user A will be operated as a bridgeand if a specific device has to be operated as a bridge, which devicewill be operated as the bridge is performed by the fourth device 210operating as a gateway has been described as described above.

FIG. 8 shows a procedure for changing a bridge into another devicedepending on the status of a device in accordance with a thirdembodiment.

Concretely, as can be seen with reference to FIG. 8, a user A owns afirst device 110 operating as a gateway (e.g., a GW#1), a second device120 operating as a PNE#2, and a third device 130 operating as a PNE#3.It is assumed that the first device 110 is a cellular phone and thesecond device 120 and the third device 130 are portable multimediadevices.

1˜5) Illustrated procedures 1˜5 are similar to those of FIG. 7 and thusare not described, and the description of FIG. 7 is referred.

6) When a discovery procedure is completed, the third device 130 isdetermined as a bridge according to a bridge determination procedure,and the bridge is activated.

7) If the third device 130 is determined as the bridge, the third device130 and a fourth device 210 perform a PN#2 establishment procedure.

8) Meanwhile, if the status of the third device 130 is no longerdifficult to operate as the bridge, a bridge change procedure isperformed.

Concretely, if the third device 130 is difficult to no longer operate asthe bridge as a result of the check of its own status, the third device130 transmits an event notification message to the first device 110,that is, a gateway. Here, the meaning that the third device 130 is inthe status in which it difficult to no longer operate as the bridge canbe a status in which the third device 130 does not have sufficient poweror a user does not want the third device 130 to operate as a bridge. Theevent notification message can be transmitted according to a DeviceManagement (DM) protocol. The event notification message can includeinformation on the status.

If the third device 130 is not suitable for being operated as the bridgeafter the first device 110 checks the event notification message, thefirst device 110 transmits a new bridge request message to the thirddevice 130. The new bridge request message can include one or more ofinformation on the status of the third device and configurationinformation of the user.

The third device 130 transmits the received new bridge request messageto the fourth device 210.

When the fourth device 210 receives the new bridge request message, thefourth device 210 selects a suitable bridge by checking the informationon the status of the third device and the configuration information ofthe user within the message.

In FIG. 8, for example, the fourth device 210 determines that the seconddevice 120, that is, the PNE#2, operates as a bridge.

The fourth device 210 transmits a bridge request message to the seconddevice 120.

When the second device 120 receives the bridge request message, thesecond device 120 transmits the bridge request message to the firstdevice 110, that is, the gateway of the PN#1, to which the second device120 belongs.

When the first device 110 receives the bridge request message, the firstdevice 110 determines whether or not to operate the second device 120 asa bridge based on user setting, etc.

If the second device 120 is determined to be operated as the bridge, thefirst device 110 transmits a bridge response message, including anindicator indicative of allowance, to the second device 120. The bridgeresponse message can further include information on the PN#1.Furthermore, the bridge response message can further include informationon the status of devices that belong to the PN#1.

When the second device 120 receives the bridge response message, thesecond device 120 checks whether a bridge operation is allowed or not bychecking the indicator within the bridge response message.

If it is checked that the bridge operation is allowed by the indicator,the second device 120 activates the bridge and transmits a bridgeresponse message to the fourth device 210.

Meanwhile, the first device 110 transmits a bridge deactivation requestmessage to the third device 130. The bridge deactivation request messageincludes information on the newly determined bridge, for example,information on the PNE#2.

When the bridge deactivation request message is received, the thirddevice 130 checks information within the message. If it is checked thatthe newly determined bridge normally operates, the third device 130deactivates its own bridge and transmits a bridge deactivation responsemessage to the first device 110.

9) Meanwhile, after the second device 120 is determined as the bridge,the second device 120 and the fourth device 140 perform a PN#2establishment procedure.

FIG. 9 shows a procedure using content or service after operating as abridge in accordance with the first to third embodiments.

Concretely, as can be seen with reference to FIG. 9, the user A owns afirst device 110 operating as a gateway (e.g., a GW#1), a second device120 operating as a PNE#2, and a third device 130 operating as a PNE#3.It is assumed that the first device 110 is a cellular phone and thesecond device 120 and the third device 130 are portable multimediadevices.

1˜5) Illustrated procedures 1˜5 are similar to those of FIG. 7 and thusare not described in detail, and the description of FIG. 7 is referred.

6) When a discovery procedure is completed, the second device 120 isdetermined as a bridge according to a bridge determination procedure,and the bridge is activated.

7) After the second device 120 is determined as the bridge, the seconddevice 120 and the fourth device 140 perform a PN#2 establishmentprocedure.

8) If a CPNS server 300 has content to be transmitted to the thirddevice 130 through the second device 120 operating as the bridge, theCPNS server 300 transmits the content to a fourth device 210. The fourthdevice 210 transmits the content to the second device 120 operating asthe bridge.

Thus, the second device 120 transmits the content to the first device110, that is, its own gateway. The first device 110 transmits thecontent to the third device 130. The third device 130 uses the contentand transmits a response message to the first device 110. The firstdevice 110 transmits the response message to the second device 120operating as the bridge, and the second device 120 transmits theresponse message to the fourth device 210.

9) Meanwhile, the second device 120 may operate as the bridge, but mayreceive and use content therefor. A person having ordinary skill in theart can easily know these procedures with reference to the procedure of8, and thus these procedures are not described in detail.

FIG. 10 shows an architecture after mode is changed.

As can be seen with reference to FIG. 10, each of second, third, andfourth devices 120, 130, and 210 includes a physical layer, a MAC layer,a 3^(rd) layer, a CPNS-enabled entity, and an application layer. Here, aPNE is driven within each of the CPNS-enabled entities of the seconddevice 120 and the third device 130, and a gateway entity is drivenwithin the CPNS-enabled entity of the fourth device 210.

As indicated by a thick solid line of FIG. 10, service data istransmitted to the second device 120 via the CPNS-enabled entity, the3^(rd) layer, the MAC layer, and the physical layer of the fourth device210. When the second device 120 receives the service data, the PNE ofthe CPNS-enabled entity receives the service data through the physicallayer, the MAC layer, and the 3^(rd) layer and then transmits theservice data to the third device 130 through the 3^(rd) layer, the MAClayer, and the physical layer.

FIG. 11 shows an example in which two devices operate as bridges.

First, FIG. 11(a) illustrates two PNs, a CPNS server, and an applicationserver. The PN#1 of the two PNs has been generated by a user A. The PN#1includes the devices of a user A and can include, for example, a GW#1, aPNE#1, a PNE#2, and a PNE#3 as shown. Here, it is assumed that the GW#1is the cellular phone of the user A and the PNE#1, the PNE#2, and thePNE#3 are the portable multimedia devices of the user A. Meanwhile, thePN#2 of the two PNs includes a GW#2 and a PNE#5. The application servercan provide service to the PNE of each PN through the CPNS server, theGW#1, and the GW#2.

Meanwhile, the user A wants to receive service provided by the PN#2.However, there is a disadvantage in that the user A cannot receive theservice provided within the PN#2 if the user A does not move to thecoverage of the PN#2 geographically.

In order to solve the disadvantage, if the PNE#2 within the PN#1 and thePNE#5 within the PN#2 can communicate with each other as in FIG. 11(b),the PNE#1 and the PNE#5 can be operated as bridges and thus the user Acan be provided with the service within the PN#2.

The above solution is described in more detail with reference to FIGS.12 and 13.

FIG. 12 shows a procedure for operating two devices as bridges inaccordance with a fourth embodiment.

As shown in FIG. 12, a user A owns a first device 110 operating as agateway (e.g., a GW#1), a second device 120 operating as a PNE#2, and athird device 130 operating as a PNE#3. It is assumed that the firstdevice 110 is a cellular phone and the second device 120 and the thirddevice 130 are portable multimedia devices. Furthermore, a serviceprovider owns a fourth device 200 operating as a gateway (e.g., a GW#2)and a fifth device 220 operating as a PNE#5.

1) When the first device 110, the second device 120, and the thirddevice 130 of the user A are located a short way off, a physicalconnection procedure is performed. Furthermore, when the fourth device210 and the fifth device 220 of the service provider are located a shortway off, a physical connection procedure is performed.

2) Next, a mutual discovery procedure is performed between the firstdevice 110, the second device 120, and the third device 130.Furthermore, a mutual discovery procedure is performed between thefourth device 210 and the fifth device 220.

3) The first device 110, the second device 120, and the third device 130generate a PN#1 by performing a PN establishment procedure therebetween.Likewise, the fourth device 210 and the fifth device 220 generate a PN#2by performing a PN establishment procedure therebetween.

Meanwhile, it is assumed that the first device 110 of the user A 110 haswanted to receive service from the service provider, but has failed indiscovering the fourth device 210, that is, the GW#2 of the serviceprovider in a discovery procedure.

4) Thus, the first device 110 performs a bridge determination procedurein order to receive the service from the fourth device 210, that is, theGW#2 of the service provider.

Concretely, the first device 110 transmits a request message to thesecond device 120 operating as a PNE.

In response thereto, the second device 120 performs a physicalconnection procedure with devices to which the second device 120 can bephysically connected nearby, for example, the fifth device 220. When thephysical connection is completed, the second device 120 transmits adiscovery request message, for example, an entity discovery requestmessage to the fifth device 220. The entity discovery request messageincludes an element including information on the PN#1 and an elementincluding information on the gateway GW#1.

In response to the reception of the discovery request message, the fifthdevice 220 transmits a discovery response message, for example, anentity discovery response message to the second device 120. Here, thefifth device 220 includes a PN info element, including information onthe PN#2 owned by the fifth device 220, and an element, includinginformation on the gateway GW#2, in the entity discovery responsemessage.

When the second device 120 receives the entity discovery responsemessage, the second device 120 extracts information from the elementswithin the message and transmits the extracted information to the firstdevice 110. Likewise, the fifth device 220 extracts information from theelements within the entity discovery request message and transmits theextracted information to the fourth device 210.

The first device 110 and the fourth device 210 check whether or notthere can be connected to each other through the second device and thefifth device based on the information. If the first device 110 and thefourth device 210 can be connected to each other through the seconddevice and the fifth device, the first device 110 determines to operatethe second device, that is, the PNE#2, as a bridge.

Next, the first device 110 transmits a bridge request message to thesecond device 120. The second device 120 transmits the bridge requestmessage to the fifth device 220, and the fifth device 220 transmits thebridge request message to the fourth device 210.

When the fourth device 210 receives the bridge request message, thefourth device 210 determines to operate the fifth device, that is, thePNE#5, as a bridge and transmits the bridge request message to the fifthdevice 220.

When the fifth device 220 receives the bridge request message from thefourth device 210, the fifth device 220 activates a bridge function andtransmits a bridge response message to the fourth device 210.

The fourth device 210 transmits the bridge response message to the firstdevice 110 through the fifth device 220 and the second device 120.

When the first device 110 receives the bridge response message, thefirst device 110 transmits the bridge request message to the seconddevice 120, and the second device 120 activates the bridge function inresponse to the bridge request message received from the first device110.

When the second device 120 and the fifth device 220 operate as bridgesas described above, the PN#1 of the user A and the PN#2 of the serviceprovider can be coupled. Accordingly, the user A can be provided withservice within the PN#2 through a specific device that belongs to itsown PN#1.

FIG. 13 shows a procedure for operating two devices as bridges inaccordance with a fifth embodiment.

As shown in FIG. 13, a user A owns a first device 110 operating as agateway (e.g., a GW#1), a second device 120 operating as a PNE#2, and athird device 130 operating as a PNE#3. It is assumed that the firstdevice 110 is a cellular phone and the second device 120 and the thirddevice 130 are portable multimedia devices. Furthermore, a serviceprovider owns a fourth device 210 operating as a gateway (e.g., a GW#2)and a fifth device 220 operating as a PNE#5.

1) When the first device 110, the second device 120, and the thirddevice 130 of the user A are located a short way off, a physicalconnection procedure is performed. Furthermore, when fourth device 210and the fifth device 220 of the service provider are located a short wayoff, a physical connection procedure is performed.

2) Next, a mutual discovery procedure is performed between the firstdevice 110, the second device 120, and the third device 130.Furthermore, a mutual discovery procedure is performed between thefourth device 210 and the fifth device 220.

3) The first device 110, the second device 120, and the third device 130generate a PN#1 by performing a PN establishment procedure therebetween.Likewise, the fourth device 210 and the fifth device 220 generate a PN#2by performing a PN establishment procedure therebetween.

4) Meanwhile, the second device 120 performs a physical connectionprocedure with devices with which the second device 120 can bephysically connected, for example, the fifth device 220.

5) When the physical connection is completed, the second device 120 andthe fifth device 220 perform a discovery procedure.

Concretely, the second device 120 transmits a discovery request message,for example, an entity discovery request message to the fifth device220. The entity discovery request message includes an element includinginformation on the PN#1 and an element including information on thegateway GW#1.

In response the reception of the discovery request message, the fifthdevice 220 transmits a discovery response message, for example, anentity discovery response message to the second device 120. Here, thefifth device 220 includes a PN info element, including information onthe PN#2 owned by the fifth device 220, and an element, includinginformation on the gateway GW#2, in the entity discovery responsemessage.

When the second device 120 receives the entity discovery responsemessage, the second device 120 extracts information from the elementswithin the message and compares the extracted information with theexisting information. Likewise, the fifth device 220 also extractsinformation from the elements within the entity discovery requestmessage and compares the extracted information with the existinginformation.

If, as a result of the comparison, the extracted information isdifferent from the existing information, a discovery update procedure isperformed and a bridge determination procedure is performed. Here, twoschemes can be used.

First, in accordance with a first scheme (scheme 1), the second device120 and the fifth device 220 transmit respective discovery updaterequest messages to the first device 110 and the fourth device 210. Thediscovery update request message can include the extracted information.

The first device 110 and the fourth device 210 determine whether or notthey can be coupled through the second device 120 and the fifth device220 based on the pieces of information included in the respectivediscovery update request message.

If the first device 110 and the fourth device 210 can be coupled throughthe second device 120 and the fifth device 220, the first device 110determines to operate the second device 120, that is, the PNE#2, as abridge. Likewise, the fourth device 210 determines to operate the fifthdevice 220, that is, the PNE#5, as a bridge.

The first device 110 and the fourth device 210 transmit respectivediscovery update response messages to the second device 120 and thefifth device 220. Each of the discovery update response messages caninclude a message, an indicator, or a value that means a bridge request.

When the discovery update response message is received, the seconddevice 120 checks the message, indicator, or value included in thediscovery update response message and transmits a bridge request messageto the fifth device 220 based on a result of the check.

The fifth device 220 activates a bridge function based on the message,indicator, or value included in the bridge request message from thesecond device 120 and the discovery update response message from thefourth device 210 and transmits a bridge response message to the seconddevice 120 and the fourth device 210. When the bridge response messageis received, the second device 120 checks that the fifth device operatesas the bridge and also activates a bridge function.

Meanwhile, in accordance with a second scheme (scheme 2), if, as aresult of the comparison, the extracted information is different fromthe existing information, the second device 120 and the fifth device 220transmit respective discovery update request messages to the firstdevice 110 and the fourth device 210. Each of the discovery updaterequest messages can include the extracted information.

The first device 110 and the fourth device 210 transmit respectivediscovery update response messages to the second device 120 and thefifth device 220.

Next, the first device 110 and the fourth device 210 can be coupledthrough the second device 120 and the fifth device 220 based on thepieces of information included in the respective discovery updaterequest messages.

If the first device 110 and the fourth device 210 can be coupled throughthe second device 120 and the fifth device 220, the first device 110determines to operate the second device 120, that is, the PNE#2, as abridge. Likewise, the fourth device 210 determines to operate the fifthdevice 220, that is, the PNE#5, as a bridge.

The first device 110 and the fourth device 210 transmit the respectivebridge request messages to the second device 120 and the fifth device220.

When the bridge request message is received, the second device 120transmits the bridge request message to the fifth device 220.

The fifth device 220 activates a bridge function in response to thebridge request message from the second device 120 and the bridge requestmessage from the fourth device 210 and transmits a bridge responsemessage to the second device 120 and the fourth device 210.

When the bridge response message is received, the second device 120checks that the fifth device operates as the bridge and also activates abridge function.

When the second device 120 and the fifth device 220 operate as thebridges as described above, the PN#1 of the user A and the PN#2 of theservice provider can be coupled. Accordingly, the user A can be suppliedwith service within the PN#2 through a specific device that belongs toits own PN#1.

The aforementioned embodiments can be combined. Accordingly, each of theembodiments is not implemented only solely, but the embodiments may beimplemented in combination if necessary. The combinations can be readilyimplemented by a person having ordinary skill in the art who reads thisspecification, and thus a detailed description thereof is omitted. It ishowever to be noted that although the combinations are not described,they are not excluded from the present invention, but should beinterpreted as being included in the scope of the present invention.

The aforementioned embodiments and modified examples can be implementedby way of a variety of means. For example, the embodiments of thepresent invention can be implemented by hardware, firmware, software, ora combination of them.

In the case of implementations by hardware, a method according to theembodiments of the present invention can be implemented by one or moreApplication Specific Integrated Circuits (ASICs), Digital SignalProcessors (DSPs), Digital Signal Processing Devices (DSPDs),Programmable Logic Devices (PLDs), Field Programmable Gate Arrays(FPGAs), processors, controllers, micro controllers, micro processors,etc.

In the case of implementations by firmware or software, a methodaccording to the embodiments of the present invention can be implementedin the form of a module, a procedure, or function that performs theaforementioned functions or operations. A software code can be stored ina memory unit and driven by a processor. The memory unit can be placedinside or outside the processor, and the memory unit can exchange datawith the processor by way of a variety of known means.

For example, the methods in accordance with the present invention can bestored in a storage medium (e.g., internal memory, flash memory, or ahard disk) and can be implemented by codes or instructions within asoftware program capable of being executed by a processor (e.g., a microprocessor). This is described below with reference to FIG. 13.

FIG. 14 is a block diagram of a device in accordance with theembodiments of the present invention.

As shown in FIG. 14, a device 100 includes storage means 101, acontroller 102, and a transceiver unit 103.

The storage means 101 stores the methods shown in FIGS. 2 to 13.

The controller 102 controls the storage means 101 and the transceiverunit 103. Concretely, the controller 102 executes the methods stored inthe storage means 101. Furthermore, the controller 102 transmits theabove-described signals through the transceiver unit 103.

The aforementioned embodiments are results in which the elements andcharacteristics of the present invention are combined in a specificform. Each of the elements or characteristics has to be considered to beoptional unless otherwise described explicitly. Each of the elements orcharacteristics can be implemented in such a way as not to be combinedwith another element or characteristic. Furthermore, some of theelements and/or the characteristics may be combined to form anembodiment of the present invention. Order of the operations describedin the embodiments of the present invention can be changed. Some of theelements or characteristics of one embodiment can be included in theother embodiment or can be replaced with corresponding elements orcharacteristics of the other embodiment. It is evident that in theclaims, an embodiment can be constructed by combining claims not havingan explicit citation relation or can be included as a new claim byamendments after an application.

The present invention can be materialized in a specific form withoutdeparting from the spirit and essential characteristics of the presentinvention. Accordingly, the detailed description should not be construedas being limited from all aspects, but should be considered to be beingillustrative. The scope of the present invention should be determined byreasonable analysis into the attached claims, and all changes within anequivalent range of the present invention fall within the scope of thepresent invention. Furthermore, in the claims, an embodiment can beconstructed by combining claims not having an explicit citation relationor can be included as a new claim by amendments after an application.

The invention claimed is:
 1. A method of communicating data in awireless communication system including a sever communicating with aplurality of devices, the method comprising: determining, by a firstdevice which operates as a gateway mode and which belongs to a firstnetwork, whether the first device is able to discover a second network;if the first device is unable to discover the second network,transmitting, by the first device, a discovery request message to asecond device, which belongs the first network and which operates as anentity mode; in response to the discovery request message, receiving, bythe first device from the second device, a discovery response messageincluding information on a third device belonging to the second network;and transmitting, by the first device to the second device, a bridgerequest message to enable the second device operates as a bridge forcoupling the first network and the second network, wherein a deviceoperating as the entity mode communicates with the server via a deviceoperating as the gateway mode.
 2. The method of claim 1, wherein thethird device operates as the entity mode in the second network.
 3. Themethod of claim 1, wherein the third device operates as the gateway modein the second network.
 4. The method of claim 1, wherein the firstdevice is a Converged Personal Network Service (CPNS)-enabled entity. 5.The method of claim 1, wherein the first network is a first PersonalArea Network (PAN) and the second network is a second PAN.
 6. A devicecommunicating data in a wireless communication system including a severcommunicating with a plurality of devices, the device comprising: atransceiver configured to transmit and receive a signal; and a processorcoupled to the transceiver and configured to: when the device operatesas a gateway mode and which belongs to a first network, determinewhether the device is able to discover a second network; if the deviceis unable to discover the second network, transmit a discovery requestmessage to a first entity, which belongs the first network and whichoperates as an entity mode; in response to the discovery requestmessage, receive, from the first entity, a discovery response messageincluding information on a second entity belonging to the secondnetwork; and transmit, to the first entity, a bridge request message toenable the first entity operates as a bridge for coupling the firstnetwork and the second network, wherein a device operating as the entitymode communicates with the server via a device operating as the gatewaymode.
 7. The device of claim 6, wherein the second entity operates asthe entity mode in the second network.
 8. The device of claim 6, whereinthe second entity operates as the gateway mode in the second network. 9.The device of claim 6, wherein the device is a Converged PersonalNetwork Service (CPNS)-enabled entity.
 10. The device of claim 6,wherein the first network is a first Personal Area Network (PAN) and thesecond network is a second PAN.